CVE-2026-55960
Un-negotiated Raw Public Key (RFC 7250) accepted in place of X.509, bypassing chain validation
Description
Un-negotiated Raw Public Key (RFC 7250) accepted in place of an X.509 certificate, bypassing chain validation. A raw public key has no chain, so ParseCertRelative() accepts it without performing any trust verification; it must therefore only be accepted when RPK was actually negotiated for that peer. The check now defaults the expected type to X.509 (per RFC 7250/8446) when no type was negotiated, comparing against the received server certificate type on the client and the selected client certificate type on the server, and rejects any mismatch, including an un-negotiated raw public key, with UNSUPPORTED_CERTIFICATE. Only affects builds with Raw Public Key support (HAVE_RPK) enabled - disabled by default in a standalone build, but included in --enable-all.
INFO
Published Date :
June 25, 2026, 7:31 p.m.
Last Modified :
June 25, 2026, 7:31 p.m.
Remotely Exploit :
Yes !
Source :
wolfSSL
Affected Products
The following products are affected by CVE-2026-55960
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | 50d2cd11-d01a-48ed-9441-5bfce9d63b27 | ||||
| CVSS 4.0 | HIGH | [email protected] |
Solution
- Update to the latest version with security fixes.
- Enable and configure Raw Public Key support correctly.
- Verify certificate type negotiation with peers.
- Reject unsupported certificate types.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-55960 vulnerability anywhere in the article.